Add tempo tuning section #830
Open
+354
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
jshaughn
requested changes
Nov 14, 2024
| #### Resources consumption | ||
|
|
||
| Grafana Tempo is a powerful tool, but it can lead to performance issues when not configured correctly. | ||
| The following configuration can lead to OOM issues for simple queries in the query-frontend component: |
There was a problem hiding this comment.
Suggested change
| The following configuration can lead to OOM issues for simple queries in the query-frontend component: | |
| For example, the following configuration is not recommended and may lead to OOM issues for simple queries in the query-frontend component: |
| ``` | ||
|
|
||
| These resources are shared between all the Tempo components. | ||
| Instead of applying the resources globally, they can be applied to each specific component, when needed: |
There was a problem hiding this comment.
Suggested change
| Instead of applying the resources globally, they can be applied to each specific component, when needed: | |
| When needed, apply resources to each specific component, instead of applying the resources globally: |
|
|
||
| #### Caching | ||
|
|
||
| Tempo can use [a cache](https://grafana.com/docs/tempo/latest/operations/caching/) that acts in different levels that is used by default with Tanka and Helm deployment examples. It uses external cache, supporting Memcached and Redis. |
There was a problem hiding this comment.
Suggested change
| Tempo can use [a cache](https://grafana.com/docs/tempo/latest/operations/caching/) that acts in different levels that is used by default with Tanka and Helm deployment examples. It uses external cache, supporting Memcached and Redis. | |
| Tempo offers multi-level [caching](https://grafana.com/docs/tempo/latest/operations/caching/) that is used by default with Tanka and Helm deployment examples. It uses external cache, supporting Memcached and Redis. |
|
|
||
| #### Dedicated attribute columns | ||
|
|
||
| When used the storage format vParquet3, defining [dedicated attribute columns](https://grafana.com/docs/tempo/latest/operations/dedicated_columns/) can improve the query performance. |
There was a problem hiding this comment.
Suggested change
| When used the storage format vParquet3, defining [dedicated attribute columns](https://grafana.com/docs/tempo/latest/operations/dedicated_columns/) can improve the query performance. | |
| When using the vParquet3 storage format , defining [dedicated attribute columns](https://grafana.com/docs/tempo/latest/operations/dedicated_columns/) can improve the query performance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref. kiali/kiali#7769
https://deploy-preview-830--kiali.netlify.app/docs/configuration/p8s-jaeger-grafana/tracing/tempo/#tempo-tunning